This gateway can read BACnet data from your BACnet IP devices and publish it as BACnet MSTP data.

It can also write to the BACnet IP devices.

This gateway can also do the reverse, read BACnet MSTP data and publish it as BACnet IP data.

It can also write to the BACnet MSTP devices.

In summary, this gateway can act as:

Client/Master on the BACnet IP network: Hence it is capable of reading data from the various BACnet slave devices and writing data to them if required.

Server/Slave on the BACnet IP network: You can use the gateway in this mode if you have a BACnet IP master on the network which would be reading data from the gateway.

Client/Master on the BACnet MSTP network: Hence it is capable of reading data from the various BACnet MSTP devices and writing data to them if required.

Server/Slave on the BACnet MSTP network: The gateway can be configured to be a server of data values, hence another BACnet MSTP client can read data from the gateway and write data into the gateway.

Block Diagram:

• On the site we have thermostats that can provide data output on BACnet IP.
• The site has a BACnet MSTP based Controller that needs the temperature data from the Thermostats.
• Since the Thermostats provide data output on BACnet IP and the controller understands only BACnet MSTP a direct data exchange is not possible.

Block Diagram:

Solution:

The devices can not directly communicate with each other as they are not on the same protocol. BACnet IP is an Ethernet based protocol, and BACnet MSTP is a Serial Protocol. You need something that will convert data from BACnet MSTP device to BACnet IP and vice versa.

ProtoConvert’s BACnet IP to BACnet MSTP converter will be an excellent solution for this requirement. The gateway reads data from the Thermostat on BACnet IP. It caches this data internally and then provides it on BACnet MSTP when requested from the Controller. 

• On the other site we have Chiller that can provide data output on BACnet MSTP.
• The site has a building management system on BACnet IP that needs the data from the Chillers.
•  Since the Chiller provides data output on BACnet MSTP and the building management system understands only BACnet IP and a direct data exchange is not possible.

Block Diagram

Solution:

The devices can not directly communicate with each other as they are not on the same protocol. BACnet IP is an Ethernet based protocol, while BACnet MSTP is a Serial Protocol. You need something that will convert data from BACnet MSTP device to BACnet IP and vice versa.

ProtoConvert’s BACnet MSTP to BACnet IP converter will be an excellent solution for this requirement. The gateway reads data from the Chillers on BACnet MSTP. It caches this data internally and then provides it on BACnet IP when requested from the BMS.

BACnet IP:

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

Like the Control and Information Protocol (CIP) used in industrial application, BACnet uses objects to represent data on a network. Objects defined by the BACnet specification include Analog Input, Analog Output, Analog Value, Binary Input, Binary Output, Binary Value, Multi-State Input, Multi-State Output, Calendar, Event-Enrollment Program, Schedule, Command, and Device.

The BACnet protocol is a completely non-proprietary open communication software standard. The standard is now controlled by the ANSI (American National Standards Institute) and ASHRAE (American Society of Heating Refrigeration and Air-Conditioning Engineers) Standard 135- 1995. In June of 1995, ASHRAE adopted BACnet as a standard for the Building Automation industry.

BACNet MSTP:

MS/TP is exclusive to BACnet and can be implemented using the EIA-485 signaling standard. This is a shielded twisted-pair (STP) LAN operating at speeds from 9.6Kbit/s to 76.0Kbit/s. This LAN type is particularly suitable for single controller and low cost communications.

Like the Control and Information Protocol (CIP) used in industrial application, BACnet uses objects to represent data on a network. Objects defined by the BACnet specification include Analog Input, Analog Output, Analog Value, Binary Input, Binary Output, Binary Value, Multi-State Input, Multi-State Output, Calendar, Event-Enrollment Program, Schedule, Command, and Device.
The BACnet protocol is a completely non-proprietary open communication software standard. The standard is now controlled by the ANSI (American National Standards Institute) and ASHRAE (American Society of Heating Refrigeration and Air-Conditioning Engineers) Standard 135- 1995. In June of 1995, ASHRAE adopted BACnet as a standard for the Building Automation industry.